Summary

This PR adds resource sizing reminder comments to all database services across the samples repository to help users understand they should adjust resource limits as needed for their deployments.

Problem

Database services in compose files lacked guidance on resource sizing, which could lead to out-of-memory errors or suboptimal performance in production deployments. Users needed clear reminders to configure appropriate resource reservations for their database containers.

Solution

Added standardized commented deploy blocks to all database services (Redis, PostgreSQL, MongoDB, MySQL) with placeholder resource reservations:

    # Adjust resources as needed
    #deploy:
    #  resources:
    #    reservations:
    #      cpus: "1.0"
    #      memory: 512M

Changes Made

• 17 compose files updated with database service sizing comments
• Database types covered: Redis, PostgreSQL (including pgvector), MongoDB, MySQL
• Services identified:
  • Redis services in 6 files (bullmq-bullboard-redis, crew-django-redis-postgres, django-celery, django-channels-redis-postgres, nounly, redis-js)
  • PostgreSQL services in 10 files (crew-django-redis-postgres, django-celery, django-channels-redis-postgres, django-postgres, fastapi-postgres-pubsub, fastapi-postgres, hasura, huginn, jupyter-postgres, nextjs-postgres, rails)
  • MongoDB services in 2 files (golang-mongodb, sveltekit-mongodb)
  • MySQL services in 1 file (svelte-mysql)

Implementation Details

• Created automated detection script to identify database services by Docker image names
• Handled various service naming patterns including hyphens (redis-service, postgres-service)
• Preserved existing deploy blocks where already present (nounly, rails, svelte-mysql, sveltekit-mongodb)
• Added comments in appropriate locations within service definitions
• Maintained consistent formatting across all files

Verification

• All database services now include resource sizing reminders
• No duplicate comments added to services with existing deploy blocks
• Format matches the specified requirements exactly
• No impact on existing functionality or deployment behavior

This change provides clear guidance to users about resource configuration while maintaining backward compatibility with existing deployments.

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

Samples Checklist

✅ All good!